If you place more than one iPart on a page, you might need to specify the order in which actions occur on that page. The commit sequence function allows you to explicitly define the execution order of multiple iParts in a content record.
You can define a commit sequence value for the processing order of each iPart relative to the other iParts in the same content record. The commit sequence value must be zero or greater. iParts with a value of zero (the default) are processed after any other iParts with a non-zero commit sequence value that are in the same content record.
Setting a commit sequence is only required in a few scenarios and is noted in an iPart’s configuration help if needed.